Conversation
Signed-off-by: Connor Tsui <connor.tsui20@gmail.com>
Merging this PR will improve performance by 18.36%
Performance Changes
Comparing 
Footnotes
|
|
We should optimize for small issue descriptions and someone familiar with the fuzzer. |
|
I am very happy to hide more of the issue, I just really don't want to scroll past instructions I already know each time I open a fuzzer issue |
|
In that case can we hide all of the Claude output? It's a huge wall of text that in my experience has rarely been useful. And if we want to optimize for readability and convenience we should hide the debug output completely as well because that also usually tells us nothing more than the backtrace already gives us. I can keep going, but to me this conversation makes zero sense when we can just collapse everything into details. The current template is already small enough that you don't need to scroll to anything. |
joseph-isaacs
left a comment
joseph-isaacs
left a comment
There was a problem hiding this comment.
LG, I am bad at reading diff markdown
2 participants
Summary
From #6936 I do not understand why we are so against being descriptive in these templates given most of what claude says is complete nonsense. If we want concision, the reproduction steps still need to make sense.
This changes the fuzzer template to have 2 different details sections, one with a full and correct description of how to reproduce, and the other with a single command for people who know what they are doing. The maintainers do not need to look at the first section.
Testing
N/A